Flash SuperSU using TWRP recovery and Root any Android device. |
您所在的位置：网站首页 › how to flash supersu zip via twrp recovery › Flash SuperSU using TWRP recovery and Root any Android device. |
Flash SuperSU using TWRP recovery and Root any Android device.
Flash SuperSU using TWRP recovery and Root any Android device. Hannah Camila ·Follow 3 min read·Sep 8, 2017-- SuperSU Root is the best ever Android rooting tool in the present. This is an another great invention by Chainfre. Chainfire can be named as the leading Android rooting team in the Android world. Before starting the rooting process user must need to unlock the bootloader and have a custom recovery. SuperSU Root is a superuser management tool which manages the rooting permissions on the Android device. This can be named as the most popular rooting tool ever. It gives more privileges to users when the rooting process done. SupurSU Root gives recovery flashable zip file for SuperSU which contains the SuperSU app and the binaries required to get root access. How to Flash SuperSU zip via TWRP Recovery· Download the SuperSU Root file first to your Android device · After the downloading process Boot your device into TWRP recovery mode · Tap in the install button and select the SuperSU Zip file · After the selecting the zip file user must need to confirm flash by swipe up the menu · After the flash process done user will give the reboot option · Reboot the device to end the process. After completing those above steps successfully your device get root under the SuperSU Root device. SuperSU Root Download Any Android deviceRight now SuperSU Root Apk is compatible with all Android versions including the new Android version Nougat 7.0. This can be named as the best ever Android version released by the Android developer. With the release of the Android 7.0 to the public SuperSU Apk application will released to the public with number of new features added to the New SuperSU Apk application. Right now any user can download SuperSU Apk Android 7.0 Nougat version. Latest SuperSU Root Changelogs14.01.2017 — SuperSU Root v2.79 Fix erroneously deleting SuperSU’s copy of app_process on 6.0 since 2.79-SR1GUI: Fix app_process requirement detection when supersu context usedFully eliminate sugote binary, no longer needed due to SELinux handling improvements in earlier versionsSupport /system/xbin/sush as default shellAdjust LD_PRELOAD filtering to exclude suhide’s librariesZIP: Motorola: default to systemless mode03.01.2017 — SuperSU Root v2.79 supolicy: fix some segfaults(NPEs) in pre-7.0 sepolicy handlingZIP: write boot block device once instead of twice (@_alexndr)© 2017 + CCMT21.01.2016 — SuperSU Root Beta v2.67 (systemless) Improved deep sleep fix for Samsung 5.1+(systemless) Added fallback method to mounting /su on system bootsupolicy: fix bug copying system_server capabilities to initsupolicy: replaced transitions: copy capabilities and attributes, silence auditssupolicy: work-around shell-based services being executed as undefined_service on Samsung 5.1+sukernel: refuse to patch ChromeOS boot imageFSTABSYSTEMRW: flag removed; worked around remount /system r/w issueZIP: improved handling of loop devicesZIP: detect boot image partition being a symlink to a file on /data, and skip wipe if soUpdated translation files03.01.2016 — SuperSU Root Beta v2.66 (systemless) Add deep sleep fix for Samsung 5.1+supolicy — Adjust Samsung 6.0 init shellZIP: Patch recovery SELinux policyZIP: Improve su.img mounting26.12.2015 — SuperSU Root Beta v2.65 (systemless) Add /su/xbin to su.img and PATHZIP: Fixed force close issue when custom boot image is usedZIP: Reworked remounting (prevents bugged write to r/o /system on flo)ZIP: Added warning that first reboot may take a few minutes/loops20.12.2015 — SuperSU Root Beta v2.64 (systemless) Detect more boot image partition names(systemless) Blank partitions before writing to them(systemless) Ask to restore boot and recovery images on full unroot(systemless) Implement “uninstall competing Superuser apps”(systemless) Samsung: prevent “KERNEL IS NOT SEANDROID ENFORCING” warning(systemless) Cleanup system install properly if present, fixes a number of possible bootloopsZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these (“allow init kernel:security { load_policy }”)supolicy: Additional SELinux patches for M (reduced logging only)Update translations |
【本文地址】